This chapter describes the problems that can occur associated with the management of 8250 and 8260 hubs and the steps to take to resolve each problem.
NetView Version 4 Release 1 PTF #U443133 introduces a bug in the netmon daemon that impacts Nways Manager-LAN in the following ways:
PTF #U447036 for NetView Version 4 Release 1 Server will fix this problem.
If you receive the NetView for AIX error message, Fatal IP Map Error, this means that a severe problem has occurred and that some hub objects may be corrupted in ovw.
To recover the situation for a given hub object:
Nways Manager-LAN uses resolver subroutines to resolve host names into network addresses. When you perform network address translation, make sure that the file /etc/resolv.conf exists.
If the file exists, the resolve subroutines assume that the local network has an operational nameserver. If the nameserver in /etc/resolv.conf is invalid or not operational, the response time of NetView for AIX for discovering network devices and performing operations on network nodes is delayed.
Therefore, if you use a nameserver in your local network, make sure that the nameserver is functional. If you do not use a nameserver, the resolve subroutines use the file /etc/hosts for network address resolution.
When NetView for AIX discovers a network device and associates a symbol (icon) to it, the symbol type is not dynamically updated when the device's characteristics change.
In order to have the icons of network devices reflect the current status of the objects in the Nways Manager-LAN database, delete the devices from all submaps and allow them to be rediscovered.
When a hub agent with an incorrect community name is first discovered by NetView for AIX, the hub icon of the agent is displayed with a box around it. If you then set the correct community name by selecting Options -> SNMP Configuration from the NetView for AIX menu bar and perform a Demand poll, the correct hub icon is displayed, but the hub is not executable.
To restore executable behavior for the hub icon, delete the hub from all submaps and allow the hub agent to be rediscovered.
When using Bay Networks Optivity LAN 7.1, you may find that the IBM Hubs Topology or LNM Topology icons are not displayed in the NetView for AIX Root submap.
To resolve this problem, make sure that the current value of the AIX environment variable LIBPATH (LIBPATH=pathname1:pathname2: pathname3) does not contain the /usr/lnms/lib directory as its first pathname (pathname1).
To check the current LIBPATH setting, enter the command:
echo $LIBPATH
When an 8250 or 8260 hub is not discovered by polling and does not appear in the IBM Hubs Topology, follow these steps to resolve the problem:
Select Locate -> Objects to find the agent in the NetView for AIX IP Internet Map. If you cannot locate the agent, this means that the agent has not yet been discovered by NetView for AIX.
If the agent is in the NetView for AIX IP Internet Map, select it and then select Test -> Ping.
If the agent is not in the NetView for AIX IP Internet Map, use the Ping command from an AIX command window. If you have IP connectivity with the agent, check your NetView for AIX configuration (discovery switch enabled, seed file, and unmanaged networks) until netmon discovers the agent.
Select the agent in the NetView for AIX IP Internet Map and then select Test -> Demand Poll.
This table is indexed by slot enabling you to check the master status of the slot you retrieved in step c.
Use the /usr/OV/bin/ovobjprint command and check that you have all the fields corresponding to a hub added to the NetView for AIX Generic Topology Database and discovered by Nways Manager-LAN (see /usr/OV/fields/C/iub.fields for a list of fields).
Use the /usr/OV/bin/netfmt command to find the error messages logged by Nways Manager-LAN.
If everything has checked out successfully, stop and then restart ovw. Then from the IBM Hubs Topology, select Options -> Unmanage and then Options -> Manage.
When an 8260 hub contains both a DMM and an ATM Control Point and Switch (A-CPSW) module, the DMM is always the master agent. If you remove the DMM, the A-CPSW module automatically becomes master. In the IP Internet submap, the DMM hub icon changes to red to indicate that the hub cannot be pinged. In the IBM Hubs Topology, the hub icon should change to indicate that the A-CPSW module is now the master management module in the hub. The icon for an 8260 hub managed by an A-CPSW module is shown in the online book User Interface.
If the hub icon in the IBM Hubs Topology does not change or if the shape around the hub icon disappears to indicate that it is no longer executable, follow these steps to resolve the problem:
This allows the new hub icon to be displayed.
If you remove and reinsert the DMM in the hub, the DMM may not be discovered in the IBM Hubs Topology, even though a new hub icon is displayed in the IP Internet submap in NetView for AIX.
If the hub is being regularly polled, the hub icon changes to red in the IBM Hubs Topology to indicate that it is still managed by the A-CPSW module. In order for the hub's new status to be correctly displayed, follow these steps:
The hub icon is added to the IBM Hubs Topology. The red hub icon disappears when the hub is next polled (or at the next polling of the hub that was seen as managed by the A-CPSW module).
When you start the Nways Manager-LAN, hub icons are blue (unknown) until the first poll is performed. As soon as the polling is finished, the color of the icon is updated to reflect the compound status of the hub.
If the message The iubd process is not running is displayed, enter the command:
cmlstart iubd
If the icons for PSM-managed Devices appear blue in the IP Internet submap and IBM Hubs Topology, follow these steps to restore the correct color-coded status:
If an Error message is displayed when you double-click on the icon of an agent in the IP Internet window, the 8250, 8260, and 8265 Device Manager component of Nways Manager-LAN has been de-installed. In this case, you cannot execute an action on agent symbols in the IP Internet submap.
To restore executable behavior for a symbol, select its icon in the IP Internet submap and choose Modify/Describe -> Symbol.
This can be caused by the following:
After SNMP communication has been reestablished, do one of the following:
Restart iubd. Then restart iubeui by clicking on any hub menu item.
For more information on the Symbols Manager, the Nways Manager-LAN process that manages executable devices, see the online book User Interface.
After restarting iubd, a red hub icon is displayed in the IBM Hubs Topology. When you double-click on the icon, an error message is displayed.
This may occur for the reasons shown in Table 27.
Table 27. Cannot Open View for Explode Hub -- Reasons and Actions
| Possible Reason | Corrective Action |
|---|---|
| First polling is running. | Wait a few seconds and retry. |
| First polling in error. | Check the NetView for AIX log for Nways Manager-LAN messages. Ensure that preparation of Management modules has been done as specified in Automatic Handling of Management Module Changes. |
| The hub is currently in the NetView for AIX unmanaged state. | Check that this is the desired state for that hub. If it is not, use the NetView for AIX Manage function to declare this hub as managed. Then try to double-click on the hub. |
| iubd has been stopped and then restarted. During this time, a Master Management module which was master before the stop, became a slave. | Check whether the old master agent is seen as a slave in the newly discovered hubs. If this is the case, use the NetView for AIX functions to delete the red hub icon from all submaps. |
This error message occurs when the agent cannot be found in any hub managed by Nways Manager-LAN.
To resolve this problem, follow these steps:
This message means that an error occurred while retrieving the iubHubIsManaged field value for the hub. To resolve the problem, follow these steps:
This message means that an error occurred while retrieving the agent hostname. To resolve this problem, follow these steps:
This message means that an error occurred while retrieving the IP address corresponding to the agent hostname. To resolve this problem, follow these steps:
This message means that an internal error occurred. To resolve this problem, follow these steps:
If no shadow appears around the cons of Master Management modules in a Hub Level view, close and reopen the view. The correct shadow is then displayed.
8260 modules installed in an 8260 hub that is managed by an 8250 Management module (for example, EMM, TRMM, or FMM) are not recognized and are not displayed in the Hub Level view. Only 8250 modules are displayed. The Controller module is always shown in slot 17. Although there can be up to four power supplies installed, only two power supplies can be displayed.
In order to display (and manage) 8260 modules, you must install an 8260 Management module in the hub and configure the module as master.
If 8260 ATM 2-port and 3-port 155Mbps (ATMflex) modules are not displayed in a Hub Level view, check if daughter cards are installed in all the daughter card slots on the module's motherboard. If one or more daughter card slots are empty, check which module is the master agent in the hub. Then do one of the following to resolve the problem:
In a Hub Level view, 8271 and 8272 ATM/LAN Switch modules are sometimes displayed as the master agent (master management module). To resolve the problem and redisplay the correct master management module:
Another way to resolve the problem is by removing modules from the 8260 hub and re-inserting them in the following order:
If you have installed Nways Remote Monitor if the RMON-related menu items remain greyed out in the Hub Manager user interface (Hub Level views, Module Level views, and so on), run the following command from an AIX window:
/usr/CML/bin/cml.8250-60.ksh -setRmonApplicationStatus 1
To restore RMON-related menu options, you must then close and reopen all Hub Level views that are currently open.
You cannot start the PSM in the 8210 Multiprotocol Switched Services (MSS) by selecting Device Management from the module's context menu due to a hardware problem in the MSS module. This is a known problem and will be fixed in Version 1.1 of the 8210 MSS microcode.
In Hub Level views of 8260 hubs, you may find that:
This occurs when an 8260 hub is managed by an ATM Control Point and Switch (A-CPSW) module at Version 2.3.0 or higher. To manage and display all 8250 and 8260 modules in the hub, install and configure a Distributed Management Module (DMM).
Use the A-CPSW module Version 2.3.0 or higher as the master management module only to manage 8260 ATM modules.
While performing hub management tasks in Nways Manager-LAN panels in Hub Level views, you may find that selecting the Refresh pushbutton results in the following warning message instead of updating the information in the panel:
SNMP error: No such name
To resolve this problem, check to see if the hub is being managed by an ATM Control Point and Switch (A-CPSW) module. Then follow the steps suggested in one of the following situations:
If you repeatedly select the Modify pushbutton on the Thresholds panel, the Nways Manager-LAN user interface may hang. If this happens, do one of the following:
If, while working in a Hub Level view, you receive an error message when assigning a module, port, or trunk to a network segment, this may be caused by insufficient data paths left on the backplane that are unable to successfully perform the operation.
Table 28 shows the combinations of the number of segments
allowed.
Table 28. Segment Combination Table - 8250 Hubs
| Ethernet | Token-Ring | FDDI |
|---|---|---|
| 3 | 0 | 0 |
| 2 | 0 | 1 |
| 2 | 3 | 0 |
| 1 | 0 | 2 |
| 1 | 4 | 0 |
| 1 | 3 | 1 |
| 0 | 7 | 0 |
| 0 | 6 | 1 |
| 0 | 3 | 2 |
| 0 | 1 | 3 |
| 0 | 0 | 4 |
Table 29 shows the combinations of the number of segments
allowed.
Table 29. Segment Combination Table - 8260 Hubs
| Ethernet | Token-Ring | FDDI |
|---|---|---|
| 8 | 10 | 0 |
| 8 | 8 | 1 |
| 8 | 6 | 2 |
| 8 | 3 | 3 |
| 8 | 0 | 4 |
Refer to the 8250 Hub Planning and Site Preparation Guide and to the 8260 Hub Planning and Site Preparation Guide for further details and rules about maximizing the available network segments.
If stations in your network do not appear in a Module Level view, this may be due to one of the following causes:
If the coupling between Nways Nways Manager-LAN and Nways Nways Manager-ATM is stopped while the Module Level view of an ATM module is open, you cannot change the configuration settings of the ports on the module until you close and reopen the Module Level view.
When the 8250, 8260, and 8265 Device Manager and LAN Network Manager components of Nways Manager-LAN are running, the color-coded status of attached bridges in Module Level views may be incorrect.
While customizing LAN submaps (as described in the online book User Interface), you may find that you lose symbol positions that you have saved. This happens for the following reasons:
If Interprocess Communication (IPC) errors (such as Sorry I can't find the port number for iubsearch) are logged and displayed in the NetView for AIX alarm card display, follow these steps:
To minimize CPU use and memory consumption by the iubd process (for example, when Nways Manager-LAN is handling many traps), close the Hub Level view in which the hub sending the traps is displayed.
A problem of color allocation may occur if you start the end user interface of Nways Manager-LAN after starting color-consumming applications, such as Nways Traffic Monitor, Nways Switching Modules Manager, and web browsers. The IBM Hubs Topology is not displayed and one of the following messages is displayed in the nv6000.log:
Cannot allocate color map for gray78. Using optional color white. X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 88 (X_FreeColors) Serial number of failed request: 3046 Current serial number in output stream: 3048
X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 91 (X_QueryColors) Value 0xffff
To resolve this problem, open the 8250, 8260, and 8265 Device Manager user interface by double-clicking on the IBM Hub Topology icon in the Root submap before you start color-consuming applications.
You may have performance problems when running the Application Transporter (MAT) and Product Specific Modules (PSMs) with large numbers of users. This is due to resource limits in the Application Transporter. For example, you may find that the PSMs perform well when there are n network users, but that the PSMs stop working when the n+1 user accesses the network.
If this problem occurs, follow these steps:
netstat -n | grep lockmgr | wc -l
ps -eF "uname pid args" | grep lockmgr
In the message displayed, the number following -u is the current resource limit.
Then save the files.
When starting multiple NetView for AIX sessions on a management station, you may find that you cannot start more than two sessions. This limitation is caused by insufficient disk space in the file system /usr/CML/OStore/cache used to start Nways Manager-LAN daemons and processes.
You can resolve this problem by increasing the size of the file system used for the ObjectStore cache. You must increase the cache size by 5.5 MB for each additional NetView session that you want to run. To do so, follow these steps:
Note that you must enter 11,000 (11,000 x 512 bytes = 5.5 MB) for each additional NetView session that you want to run.
If you find that the response time of the NetView graphical interface is much slower than usual (for example, a long delay between mouse click and interface response), the nvot_server daemon is receiving repeated requests from the iubmap process. This happens when a large amount of system resources is required to resynchronize hub and LAN network views.
To solve the problem, you must decrease the initial synchronization priority set for the iubmap process. To do so, follow these steps:
The new value you set is valid only for the initial synchronization of the iubmap process. After initial synchronization, the priority is automatically reset to the default value 0 (Normal).
If you find that the result of a software download to a master DMM module does not appear in the Download panel, this may be because there are other (slave) DMM modules in the hub. During the download operation, the microcode is downloaded to the master DMM, but the master DMM is reset and becomes slave. The slave DMM module becomes master. The download results displayed in the panel are then the results of the last microcode download performed to the slave DMM that is now master.
To reset the DMM module that is now slave to master, choose Hub -> Control -> Reset Mastership.
If you have a problem when starting statistics for 8250 and 8260 hub resources, display the setting of the TZ (Time Zone) AIX environment variable and unset the TZ variable. (Change the TZ variable's setting to unset TZ).
When you start RMON statistics, the following message may be displayed:
The MIB variable setting failed for 8260 TR1 RMON Error Report View
Ignore this error message if you are running the statistics for an 8260 hub with a TMAC agent that receives data from a Token-Ring network that has all RMON groups enabled.
When you start Nways Manager-LAN statistics to graph the bandwidth of a Token-Ring segment by clicking on one of the Token-Ring network icons in a Hub Level view, note that the ring speed used to compute the bandwidth is 16 Mbps.
To avoid printer problems when printing Nways Manager-LAN statistics, you are recommended to use a color printer.
This message means that the agent has sent a trap that is not supported by Nways Manager-LAN. This occurs when you have an agent version that is newer than the one supported by Nways Manager-LAN.
This message means that the variables sent with the trap are not in the private MIB, or that an error occurred while decoding the variables. To resolve this problem, check the /var/opt/OV/log/trapd.log file to find the corresponding agent's trap, and check the log to find the error.
This message means that the number of variables sent with the trap does not correspond to what is expected by Nways Manager-LAN. To resolve this problem, check that your agent's version is fully supported by Nways Manager-LAN.
| Note: | If the value unknown hub is displayed instead of the hub's name, Nways Manager-LAN has received a trap sent by an agent in a hub that is not managed by Nways Manager-LAN. |
When you perform an echo test, the Echo trap from the Management module is ignored.
To display the result of the echo test, click on Stop in the Echo panel.
To avoid unexpected results in the NetView for AIX and Nways Manager-LAN user interfaces, always close the Copyright panel and pop-up messages by selecting the OK pushbutton.
To ensure that accurate information is displayed about stations on monitored 8250 token-ring networks, the following prerequisites must be met: